Release notes

Summary: Pre- and post-encounter measures related to the anchor by PatientId were outside the time interval specified in the definition configuration due to rounding.

Resolution: The pre- and post-encounter selection includes only those encounters that precisely match the time filter specified in the definition.

Summary: Following EDS 2023.3.16 patch, some non-costed transactions from Cost Detail were not included in the CostDetailCategoryCalculationReporting table when the Publish Reporting Tables job was run.

Resolution: Updates were made to include all non-costed records and accurately categorizes them as Cost Model zero.

Summary: Due to sorting and time frame ties, Encounter Measures generated different results when reprocessing with the same parameters if:

• The data contained potential pre- and post-encounters with the same admit date time and

• The configuration did not allow anchors to be in multiple returns and

• The encounters were configured to only be included in the “First” episode.

Resolution: In Clinical Encounter Measures (CEM) processing, selecting unique encounters for the "First" option adds a second sort by the encounterid field(the first sort is by day)s. This changr ensures an unambiguous sort order with the same value in the Days/Hours field.

Summary: The Publish Reporting Tables (PRT) job failed due to resource/partition overload.

Resolution: Refined partitions and PRT assets so PRT job ran successfully.

Summary: Costing variances were calculated incorrectly.

Resolution: Implemented changes to use the same Cost Per Ratio of Cost to Charge (CostPerRCC) value to calculate cost in CostResults rather than at the CostDetailCategoryCalculationReporting (CDCC) level. This change eliminated the cost variance in the following scenarios:

• CalculatedCost

• FixedCost

• FixedCPU

• VariableCost

• VariableCPU
  

Summary: In the Modify a cost model dialog, when a user clicked Back or Close, the Unsaved changes dialog was hidden behind the primary dialog.

Resolution: The Unsaved changes dialog for the cost model dialog is visible.

Summary: Users were unable to delete definitions in a Direct to Encounter (D2E) definition.

Resolution: The definition is removed if no related records are available. The dialog reflects this event.

If you delete a definition and rerun D2E for a cost model, all previous model results truncate for the specific D2E and CostDetailCategoryCalculation (CDCC) tables. No D2E data is removed from D2E_CostDetailTransactionMapping and no D2E data is removed from CostItem and Cost Relative Value Untis (CostRVU) tables.

Summary: Import errors occurred when using standard transform to add new Place of Service values to a database during CostDetail imports.

Resolution: Lengthened column to 50 characters for PlaceOfService.Description.

Summary: Data Management Engine (DME) processing task auto ran generated errors.

Resolution: The following scheduled jobs are no longer automatically scheduled to run upon install or upgrade and must be configured manually according to your organizational data import schedule:

• Trigger Import DME Data

• Trigger DME Processing

Summary: Starting and ending balance columns did not appear correctly with the Reclasses tab and Allocations tab.

Resolution: Corrected formulas on the Reclasses tab and Allocations worksheets that referencedwere the incorrect Process Group IDs.

Summary:03 Recon Reports did not display the reclass section properly for some customers.

Resolution: Modified the report to display the reclass section as intended.

Summary: Place of Service, Cost Detail, Cost Detail staging, and extract, transform, and load (ETL) fields needed to be lengthened from 5 to 25 charaters to match Epic codes.

Resolution: Columns were lengthened to 25 characters in reference tables to allow standard acceptance of source data, improve consistency across reference tables, and reduce customization.

Summary: The structure of the SQL in the transform to CostDetail from the Staging import needed to be upgraded to improve performance when updating Encounter Dirty.

Resolution: Syntax changes were made to the transform to improve performance when updating Encounter Dirty.

Summary: On the Process cost page, the Costing General Ledger (CGL) load did not clear the completed dates for reclasses and allocations.

Resolution: When importing the CGL, Clear results check boxes were marked and subsequently cleared upon processing for any previously run items on the Process cost grid. Summarization results were not marked to be cleared as part of this process.

Summary: Encounter.BillStatus data columns needed to be lengthened from 5 to 25 characters.

Resolution: Columns were lengthened to 25 characters in reference tables to accept standard source data, improve consistency across reference tables, and reduce customization.

Summary: The Save function was not successful even though no errors were present. Instead, the browser window displayed a 'Pending' spinner, the definition was not saved, and the system locked up. All processes that wrote changes to the database (such as cost processing, opening the desktop application, running ETLs, and so on) could no longer proceed and no error messages were displayed informing users of what happened.

Resolution: The Save function now works correctly without errors and associated tables are populated with the correct information. If users attempt to save something that is invalid, errors explicitly state the issue.

Summary: Previously, users were required to activate or deactivate a revenue distribution entry to track which entries applied and which were no longer active. Add revenue distribution and Edit revenue distribution pages provide the following functionality:

• Activate/deactivate entry within the entry.

• Activate/deactivate entry within the main page.

• View the entry Active status in the main page.

• View only the active entries Prevent inactive entries from being processed.

Resolution: All new functionality is now incorporated into the feature.

Resolution: Modified the Publish Reporting Tables job that uses underscores in costcat names and various costcat configurations.

Resolution: Code fixed to check for correct configuration in deciding if Provider RVU results need to be cleared.

Resolution: A new transform was added to the transform list for the CostDetail from the Staging table.

Summary: When managing manual statistic accounts in cost modeling, interactive column sorting did not work in edit mode.

Resolution: Column sorting works in edit mode by either ascending or descending order.

Summary: When processing a reclass definition, all active reclasses that were selected from other reclass versions failed during processing.

Resolution: For successful processing, reclasses with no results in the Costing General Ledger (CGL) table include only the cost model-specific reclass definitions.

Summary: You could not add entities after deleting or saving entities when modifying a cost model. If previous entities were not modified, new entries were ignored.

Resolution: Differences between the previous and new entity lists are compared, and if the entity exists in the cost model modification, it is saved.

Summary: New accounts that corresponded to added reclass account range and allocation account range were not added by default to the EDSAcct page.

Resolution: New accounts that corresponded to added reclass account range and allocation account range accounts are now added by default on the EDSAcct page.

Summary: When setting the Advanced Method Offset Account and Standard Method Offset Account in Configure System Settings, the new ACCT records were not created with Expense as an account type. Instead, they were created as an NA account type, which led to reconciliation variances when calculating cost in EDS.

Resolution: The account type was modified to be Expense when adding new Standard Method Offset Account and Advanced Method Offset Account on the System Configuration page in EDS.